#Code Quality

[shr0mwzrd]

Ohhhhhh my ducking GOD I'm gonna lose it at my job rn.

So like. We recently had a "strategic downsizing* that affected mostly management positions due to our sole investor having a poor financial situation on their end. As a result, there's been a refocus on the part of our product that actually makes money, and a reshuffle of personal.

I've been on team A for my entire 1.5 years hear (since Nov 2021.) I'm meant to be on team B long-term, but I'm temporarily being loaned to team C for the next few months.

Team C's codebase is, to put it mildly, absolute fucking shit. For context, we recently had to do a complete refactor of our Finance systems, and the systems under team C has everything that was wrong with Finance AND MORE.

To make it worse, I just found out that 2 of the 3 other people on team C who have my same title (software development engineer 1) and have worked at this company for the same amount OR LESS are getting promoted to developer 2, and the 3rd is on the shortlist for the same. Y'know, the same folks responsible for the worst code I've ever seen in my life. But they're all cishet men, and I'm just a silly little tranny faggot 🙃🙃🙃

I fucking hate it here. Actively looking for WFH coding work if anybody has any decent leads.

[jacelynsia]

Why Rushing into Coding Can Doom Your Software Project

Jumping straight into writing code without proper planning can lead to costly mistakes, rework, and project failure. Learn why a strategic approach, including requirements gathering and design, is essential for successful software development.

[devopsenabler1-blog]

Driving Innovation: A Case Study on DevOps Implementation in BFSI Domain

Banking, Financial Services, and Insurance (BFSI), technology plays a pivotal role in driving innovation, efficiency, and customer satisfaction. However, for one BFSI company, the journey toward digital excellence was fraught with challenges in its software development and maintenance processes. With a diverse portfolio of applications and a significant portion outsourced to external vendors, the company grappled with inefficiencies that threatened its operational agility and competitiveness. Identified within this portfolio were 15 core applications deemed critical to the company’s operations, highlighting the urgency for transformative action.

Aspirations for the Future:

Looking ahead, the company envisioned a future state characterized by the establishment of a matured DevSecOps environment. This encompassed several key objectives:

Near-zero Touch Pipeline: Automating product development processes for infrastructure provisioning, application builds, deployments, and configuration changes.

Matured Source-code Management: Implementing robust source-code management processes, complete with review gates, to uphold quality standards.

Defined and Repeatable Release Process: Instituting a standardized release process fortified with quality and security gates to minimize deployment failures and bug leakage.

Modernization: Embracing the latest technological advancements to drive innovation and efficiency.

Common Processes Among Vendors: Establishing standardized processes to enhance understanding and control over the software development lifecycle (SDLC) across different vendors.

Challenges Along the Way:

The path to realizing this vision was beset with challenges, including:

Lack of Source Code Management

Absence of Documentation

Lack of Common Processes

Missing CI/CD and Automated Testing

No Branching and Merging Strategy

Inconsistent Sprint Execution

These challenges collectively hindered the company’s ability to achieve optimal software development, maintenance, and deployment processes. They underscored the critical need for foundational practices such as source code management, documentation, and standardized processes to be addressed comprehensively.

Proposed Solutions:

To overcome these obstacles and pave the way for transformation, the company proposed a phased implementation approach:

Stage 1: Implement Basic DevOps: Commencing with the implementation of fundamental DevOps practices, including source code management and CI/CD processes, for a select group of applications.

Stage 2: Modernization: Progressing towards a more advanced stage involving microservices architecture, test automation, security enhancements, and comprehensive monitoring.

To Expand Your Awareness: https://devopsenabler.com/contact-us

Injecting Security into the SDLC:

Recognizing the paramount importance of security, dedicated measures were introduced to fortify the software development lifecycle. These encompassed:

Security by Design

Secure Coding Practices

Static and Dynamic Application Security Testing (SAST/DAST)

Software Component Analysis

Security Operations

Realizing the Outcomes:

The proposed solution yielded promising outcomes aligned closely with the company’s future aspirations. Leveraging Microsoft Azure’s DevOps capabilities, the company witnessed:

Establishment of common processes and enhanced visibility across different vendors.

Implementation of Azure DevOps for organized version control, sprint planning, and streamlined workflows.

Automation of builds, deployments, and infrastructure provisioning through Azure Pipelines and Automation.

Improved code quality, security, and release management processes.

Transition to microservices architecture and comprehensive monitoring using Azure services.

The BFSI company embarked on a transformative journey towards establishing a matured DevSecOps environment. This journey, marked by challenges and triumphs, underscores the critical importance of innovation and adaptability in today’s rapidly evolving technological landscape. As the company continues to evolve and innovate, the adoption of DevSecOps principles will serve as a cornerstone in driving efficiency, security, and ultimately, the delivery of superior customer experiences in the dynamic realm of BFSI.

Contact Information:

Phone: 080-28473200 / +91 8880 38 18 58

Email: sales@devopsenabler.com

Address: DevOps Enabler & Co, 2nd Floor, F86 Building, ITI Limited, Doorvaninagar, Bangalore 560016.

[lastfry]

Explained in Depth: The IndentationError - Expected an Indented Block

The IndentationError: expected an indented block is an error commonly encountered in programming languages like Python that rely on indentation to define the structure of code blocks. Unlike languages that use braces {} or keywords like begin and end to denote blocks of code, Python uses indentation to signify the beginning and end of code blocks.

This error occurs when the interpreter or compiler encounters a situation where it expects a properly indented code block but does not find one. There are several common reasons for this error:

Mismatched Indentation Levels: This occurs when there is inconsistency in the number of spaces or tabs used for indentation within a code block. Mixing spaces and tabs or using different numbers of spaces can lead to this error.

Missing Colon at the End of a Control Flow Statement: Python uses colons (:) to indicate the beginning of a new code block, such as with if, else, for, or while statements. Omitting the colon after such statements can result in an IndentationError.

Empty Code Blocks: Having an empty code block without any indented statements can also trigger this error. For example, defining a function without any indented code inside it can lead to an IndentationError.

To resolve the IndentationError: expected an indented block, it is essential to review the code and ensure the following:

Consistent indentation: Use either spaces or tabs consistently throughout the code, avoiding mixing them within the same block.

Correct colon placement: Verify that control flow statements (such as if, else, for, while) are followed by a colon, indicating the start of a new code block.

Meaningful code inside blocks: Ensure that code blocks, such as functions or control flow statements, contain meaningful indented code inside them.

By paying attention to these factors and maintaining consistent indentation practices, develop

if you like to learn more about it then please visit analyticsjobs.in

[infernal-lamb]

Searching your eyes for the saint is an act of futility

something that's just been on my mind recently!

[reds-skull]

Soap "dog-coded" MacTavish my beloved

(This took 5 weeks help)

[a-compass-without-a-needle]

This is what happened after 3.1 isn't it?

[taee]

👍🏻🫵🏻😜

[bulbabutt]

rise leo does know whats going on with his brothers, dont you worry

previous part | all comics in this crossover (chrono) | tip jar (kofi)

[froggyy]

PRESENTATION MICHAEL‼️💥💥

[perrieedwards]

SABRINA CARPENTER - SHORT N' SWEET POSTERS

shop for the posters here

[kateyopalescent]

I’m gonna pop your bubblegum heart

[jinikaris]

no one's safe from the lix charm, not even "ghosts" 👻

↪ SKZ CODE EP. 67: SKZ-ARY TOWN #1